Skip to content

Implement unary_ufunc functions using elementwise_util #9386

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: gh/swolchok/440/head
Choose a base branch
from

Conversation

swolchok
Copy link
Contributor

One less set of independent implementations to worry about going forward (e.g., we don't have to vectorize these separately from elementwise_util and they get all benefits of elementwise_util).

Copy link

pytorch-bot bot commented Mar 19, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9386

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 1 Unrelated Failure

As of commit 7baa2f4 with merge base 71025df (image):

NEW FAILURE - The following job has failed:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@swolchok
Copy link
Contributor Author

this will get shuffled later in the stack

@swolchok swolchok marked this pull request as draft March 28, 2025 20:28
return out;
}

ET_SWITCH_REALHBBF16_TYPES(in.scalar_type(), ctx, op_name, CTYPE_IN, [&] {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a problem, right? the compute dtype here would be the input's scalar type,

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you need to switch over FLOATHBF16, right?

[ghstack-poisoned]
swolchok added a commit that referenced this pull request May 28, 2025
One less set of independent implementations to worry about going forward (e.g., we don't have to vectorize these separately from elementwise_util and they get all benefits of elementwise_util).

ghstack-source-id: 11dfccc
ghstack-comment-id: 2735017402
Pull Request resolved: #9386
@swolchok swolchok changed the base branch from gh/swolchok/380/head to gh/swolchok/440/head May 28, 2025 23:57
Comment on lines +148 to +151
ScalarType compute_type = in.scalar_type() == ScalarType::Double
? ScalarType::Double
: ScalarType::Float;
ET_SWITCH_FLOAT_TYPES(compute_type, ctx, op_name, CTYPE_COMPUTE, [&] {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the only ET_SWITCH change remaining -- we are switching over the possible compute types, not the input/output types.

@swolchok swolchok temporarily deployed to upload-benchmark-results May 29, 2025 00:55 — with GitHub Actions Inactive
@swolchok swolchok temporarily deployed to upload-benchmark-results May 29, 2025 01:13 — with GitHub Actions Inactive
@swolchok swolchok temporarily deployed to upload-benchmark-results May 29, 2025 02:17 — with GitHub Actions Inactive
@swolchok swolchok temporarily deployed to upload-benchmark-results May 29, 2025 02:35 — with GitHub Actions Inactive
[ghstack-poisoned]
swolchok added a commit that referenced this pull request May 29, 2025
One less set of independent implementations to worry about going forward (e.g., we don't have to vectorize these separately from elementwise_util and they get all benefits of elementwise_util).

ghstack-source-id: 4f94633
ghstack-comment-id: 2735017402
Pull Request resolved: #9386
@swolchok swolchok marked this pull request as ready for review May 29, 2025 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants